Обновление от 08.01.2026
Инструкция предполагает, что ваш роутер сброшен до заводских настроек.
Инструкция проверена на RouterOS версии 7.20
TLDR: JWTs should not be used for keeping your user logged in. They are not designed for this purpose, they are not secure, and there is a much better tool which is designed for it: regular cookie sessions.
If you've got a bit of time to watch a presentation on it, I highly recommend this talk: https://www.youtube.com/watch?v=pYeekwv3vC4 (Note that other topics are largely skimmed over, such as CSRF protection. You should learn about other topics from other sources. Also note that "valid" usecases for JWTs at the end of the video can also be easily handled by other, better, and more secure tools. Specifically, PASETO.)
A related topic: Don't use localStorage (or sessionStorage) for authentication credentials, including JWT tokens: https://www.rdegges.com/2018/please-stop-using-local-storage/
The reason to avoid JWTs comes down to a couple different points:
| 1 | fonts.googleapis.com | 10 | |
|---|---|---|---|
| 2 | facebook.com | 10 | |
| 3 | twitter.com | 10 | |
| 4 | google.com | 10 | |
| 5 | youtube.com | 10 | |
| 6 | s.w.org | 10 | |
| 7 | instagram.com | 10 | |
| 8 | googletagmanager.com | 10 | |
| 9 | linkedin.com | 10 | |
| 10 | ajax.googleapis.com | 10 |
Javascript cloth simulation.
A CodePen by suffick.
((Ober|Unter den|An |Im |Platz |Berg |Am |Alt\-).+|(?:([A-Z][a-zäüö-]+){1,2})).([Cc]haussee|[Aa]llee|[sS]tr(\.|(a(ss|ß)e))|[Rr]ing|berg|gasse|grund|hörn| Nord|graben|[mM]arkt|[Uu]fer|[Ss]tieg|[Ll]inden|[Dd]amm|[pP]latz|brücke|Steinbüchel|Burg|stiege|[Ww]eg|rain|park|[Ww]eide|[Hh][oö]f|pfad|garten|bogen|passage).+?(\d{1,4})([a-zäöüß]+)?(\-?\d{1,4}[a-zäöüß]?)?Note: the first letter must be capitalized and there must be a house number
//city with zip code
(?| ;; Taken from https://andreyor.st/posts/2020-05-10-making-emacs-tabs-look-like-in-atom/ | |
| ;; https://github.com/andreyorst/dotfiles/blob/740d346088ce5a51804724659a895d13ed574f81/.config/emacs/README.org#tabline | |
| (defun my/set-tab-theme () | |
| (let ((bg (face-attribute 'mode-line :background)) | |
| (fg (face-attribute 'default :foreground)) | |
| (hg (face-attribute 'default :background)) | |
| (base (face-attribute 'mode-line :background)) | |
| (box-width (/ (line-pixel-height) 4))) | |
| (set-face-attribute 'tab-line nil |
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.